Skip to content

next-solver 2025h2 #318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 21, 2025
Merged

next-solver 2025h2 #318

merged 3 commits into from
Jul 21, 2025

Conversation

lcnr
Copy link
Contributor

@lcnr lcnr commented Jun 23, 2025

it didn't change much from the h1 goal ✨ notable changes:

We've fixed all the compilation errors in our benchmarks (at least when using in-progress changes) and are now testing some of our benchmarks with the new solver by default. We have already made significant progress on fixing performance regressions, we're still slower than the old solver in the relevant benchmarks
image

We've done a full crater run and fixed most issues found on crater. Given our in-progress changes there is no unintended major breakage and all intended breakage in widely used crates has been fixed.

cc @compiler-errors @BoxyUwU

Rendered

Co-authored-by: Rémy Rakic <remy.rakic+github@gmail.com>
@nikomatsakis nikomatsakis merged commit c4bb3d8 into rust-lang:main Jul 21, 2025
2 checks passed
@lcnr lcnr deleted the next-solver-cont branch July 21, 2025 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants